| Package | hl7.ehrs.ehrsfmr21 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-TI.4.3.html |
| Url | http://hl7.org/ehrs/Requirements/EHRSFMR2.1-TI.4.3 |
| Version | 2.1.0 |
| Status | active |
| Date | 2024-11-26T16:30:50+00:00 |
| Name | TI_4_3_Terminology_Mapping |
| Title | TI.4.3 Terminology Mapping (Function) |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | Map or translate one terminology to another as needed by local, regional, national, or international interoperability requirements. |
| Purpose | The ability to map or translate one terminology to another is fundamental to an organization in an environment where several terminologies are in play to meet different purposes. It is a common occurrence that data is captured using one terminology, but is shared using another terminology. Example: Within a healthcare organization there may be a need to map terminology concepts with the same semantic meaning to meet different purposes (e.g., between an EHRS and an external laboratory system, or between an EHRS and a billing system). Standard terminologies are evolving and maps will need to be adjusted to support this evolution and more sophisticated use of standard terminologies and maps over time. Realm specific (including local, regional, national or international) interoperability requirements can also determine the need for terminology mapping, and in many cases terminology mapping services (internal or external) can be used to satisfy these requirements. The interaction and mapping of terminologies may be called into question in a legal proceeding, when clinical decisions were documented or when semantic meaning could be misinterpreted. It is important to seek guidance, document and retain all mapping decisions for all types of terminology mapping, and to recognize when mapping may not be possible from one concept to another. The quality of mapping is dependent upon the skills and interpretation of standard terminologies and clinical information by mapping experts. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Map or translate one terminology to another as needed by local, regional, national, or international interoperability requirements.
The ability to map or translate one terminology to another is fundamental to an organization in an environment where several terminologies are in play to meet different purposes. It is a common occurrence that data is captured using one terminology, but is shared using another terminology.
Example: Within a healthcare organization there may be a need to map terminology concepts with the same semantic meaning to meet different purposes (e.g., between an EHRS and an external laboratory system, or between an EHRS and a billing system). Standard terminologies are evolving and maps will need to be adjusted to support this evolution and more sophisticated use of standard terminologies and maps over time.
Realm specific (including local, regional, national or international) interoperability requirements can also determine the need for terminology mapping, and in many cases terminology mapping services (internal or external) can be used to satisfy these requirements.
The interaction and mapping of terminologies may be called into question in a legal proceeding, when clinical decisions were documented or when semantic meaning could be misinterpreted. It is important to seek guidance, document and retain all mapping decisions for all types of terminology mapping, and to recognize when mapping may not be possible from one concept to another. The quality of mapping is dependent upon the skills and interpretation of standard terminologies and clinical information by mapping experts.
| TI.4.3#01 | SHALL |
The system SHALL provide the ability to manage data using terminology maps which may be provided by terminology mapping services (internal or external). |
| TI.4.3#02 | SHOULD |
The system SHOULD provide the ability to update terminology maps using standard terminology services (internal or external). |
| TI.4.3#03 | SHOULD |
The system SHOULD provide the ability to render data quality and technical quality reports for a user to determine the validity of terminology mappings using approved mapping techniques. |
| TI.4.3#04 | MAY |
The system MAY provide the ability for a user to maintain custom terminology maps using approved mapping techniques where formal standard terminology maps are unavailable. |
| TI.4.3#05 | MAY |
The system MAY provide the ability for a user to maintain custom terminology maps to formal standard terminology maps in order to support historical data use. |
FHIR{
"resourceType" : "Requirements",
"id" : "EHRSFMR2.1-TI.4.3",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Map or translate one terminology to another as needed by local, regional, national, or international interoperability requirements.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>The ability to map or translate one terminology to another is fundamental to an organization in an environment where several terminologies are in play to meet different purposes. It is a common occurrence that data is captured using one terminology, but is shared using another terminology.</p>\n<p>Example: Within a healthcare organization there may be a need to map terminology concepts with the same semantic meaning to meet different purposes (e.g., between an EHRS and an external laboratory system, or between an EHRS and a billing system). Standard terminologies are evolving and maps will need to be adjusted to support this evolution and more sophisticated use of standard terminologies and maps over time.</p>\n<p>Realm specific (including local, regional, national or international) interoperability requirements can also determine the need for terminology mapping, and in many cases terminology mapping services (internal or external) can be used to satisfy these requirements.</p>\n<p>The interaction and mapping of terminologies may be called into question in a legal proceeding, when clinical decisions were documented or when semantic meaning could be misinterpreted. It is important to seek guidance, document and retain all mapping decisions for all types of terminology mapping, and to recognize when mapping may not be possible from one concept to another. The quality of mapping is dependent upon the skills and interpretation of standard terminologies and clinical information by mapping experts.</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>TI.4.3#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to manage data using terminology maps which may be provided by terminology mapping services (internal or external).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>TI.4.3#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to update terminology maps using standard terminology services (internal or external).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>TI.4.3#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render data quality and technical quality reports for a user to determine the validity of terminology mappings using approved mapping techniques.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>TI.4.3#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability for a user to maintain custom terminology maps using approved mapping techniques where formal standard terminology maps are unavailable.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>TI.4.3#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability for a user to maintain custom terminology maps to formal standard terminology maps in order to support historical data use.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-TI.4.3",
"version" : "2.1.0",
"name" : "TI_4_3_Terminology_Mapping",
"title" : "TI.4.3 Terminology Mapping (Function)",
"status" : "active",
"date" : "2024-11-26T16:30:50+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Map or translate one terminology to another as needed by local, regional, national, or international interoperability requirements.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"purpose" : "The ability to map or translate one terminology to another is fundamental to an organization in an environment where several terminologies are in play to meet different purposes. It is a common occurrence that data is captured using one terminology, but is shared using another terminology.\n\nExample: Within a healthcare organization there may be a need to map terminology concepts with the same semantic meaning to meet different purposes (e.g., between an EHRS and an external laboratory system, or between an EHRS and a billing system). Standard terminologies are evolving and maps will need to be adjusted to support this evolution and more sophisticated use of standard terminologies and maps over time.\n\nRealm specific (including local, regional, national or international) interoperability requirements can also determine the need for terminology mapping, and in many cases terminology mapping services (internal or external) can be used to satisfy these requirements.\n\nThe interaction and mapping of terminologies may be called into question in a legal proceeding, when clinical decisions were documented or when semantic meaning could be misinterpreted. It is important to seek guidance, document and retain all mapping decisions for all types of terminology mapping, and to recognize when mapping may not be possible from one concept to another. The quality of mapping is dependent upon the skills and interpretation of standard terminologies and clinical information by mapping experts.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-TI.4.3-01",
"label" : "TI.4.3#01",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to manage data using terminology maps which may be provided by terminology mapping services (internal or external).",
"derivedFrom" : "EHR-S_FM_R1.1 IN.4.3#1"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-TI.4.3-02",
"label" : "TI.4.3#02",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to update terminology maps using standard terminology services (internal or external).",
"derivedFrom" : "EHR-S_FM_R1.1 IN.4.3#2"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-TI.4.3-03",
"label" : "TI.4.3#03",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render data quality and technical quality reports for a user to determine the validity of terminology mappings using approved mapping techniques.",
"derivedFrom" : "EHR-S_FM_R1.1 IN.4.3#3"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-TI.4.3-04",
"label" : "TI.4.3#04",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability for a user to maintain custom terminology maps using approved mapping techniques where formal standard terminology maps are unavailable.",
"derivedFrom" : "EHR-S_FM_R1.1 IN.4.3#4"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-TI.4.3-05",
"label" : "TI.4.3#05",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability for a user to maintain custom terminology maps to formal standard terminology maps in order to support historical data use."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.